Krampus Hack 2024 registrations are opened !
https://tins.amarillion.org/krampu24/
#gamejam #KrampusHack #SecretSanta
Krampus Hack 2024 registrations are opened !
https://tins.amarillion.org/krampu24/
#gamejam #KrampusHack #SecretSanta
Recently I came across a nice video showing the difference between both database.
It’s a clear win for PostgreSQL.
If ever you encounter error like this:
(159/159) checking for file conflicts [###################################################################] 100%
error: failed to commit transaction (conflicting files)
mingw-w64-i686-glib2: /mingw32/bin/gi-compile-repository.exe exists in filesystem
mingw-w64-i686-glib2: /mingw32/bin/gi-decompile-typelib.exe exists in filesystem
mingw-w64-i686-glib2: /mingw32/bin/gi-inspect-typelib.exe exists in filesystem
mingw-w64-i686-glib2: /mingw32/bin/libgirepository-2.0-0.dll exists in filesystem
...and so on...
The use the following command to update your system:
pacman -Suuy --overwrite "*"
The new stable firmware is out, with a bunch of bugfixes, new features, and new apps !!
Here you go for a detailed changelog since 2.0.0 !
First apps changes are listed, and then the UI / Radio / Baseband / Website / GIT ones.
TLDR, main features for that update:
ADSB:
AIS:
Audio:
BLE:
Capture/Recording apps:
Recon:
ERT:
Freqman:
Fileman:
Games:
Fox hunt:
Level:
Looking glass:
Mic:
POCSAG:
RadioSonde:
Settings:
TPMS:
Wardrive Map:
Weather:
Radio:
Tools/Debug:
Baseband:
USB/Serial:
UI:
Code/Build:
Git depot:
Website (https://hackrf.app):
If you are coming from a version <2.0.0, you have to first update using the classic hackrf_spiflash method to bring your firmware to a version >=2.0.0. It will only update the parts of the firmware on the flash, all external apps will NOT be updated using only hackrf_spiflash.
In a second time use the web interface at https://hackrf.app to update to lastest stable/nightly. It will ALSO update external apps that are stored on the sdcard.
If your firmware is already >= 2.0.0, just directly go to https://hackrf.app and update all in one go from there.
!! all sdcard content is NOT updated through website, only the external apps !!
Links:
https://github.com/portapack-mayhem/mayhem-firmware/releases
https://github.com/portapack-mayhem/mayhem-firmware/wiki/Update-firmware
#hackrf #portapack #mayhem #firmware #update
It was found in the upstream git repo sources, and particularly well hidden.
Original article here:
https://www.openwall.com/lists/oss-security/2024/03/29/4
See also
If you’re doing scp command, with ‘-r’ recursive option, and stumble upon a strange “path canonicalization failed” out of nowhere:
Starting from SSH 9.0.0 scp is using sFTP to copy files. And in sFTP, target directories must exist.
Simple fix: use -O, legacy mode:
“Use the legacy SCP protocol for file transfers instead of the SFTP protocol. Forcing the use of the SCP protocol may be necessary for servers that do not implement SFTP, for backwards-compatibility for particular filename wildcard patterns and for expanding paths with a `~’ prefix for older SFTP servers”
#SSH #SCP #ERROR
The reMarkable 2 tablet is an e-ink paper feel like tablet, aimed at note taking, quick drawing, and PDF/EPub reading.
You can read the product informations/hardware directly on the reMarkable website.
It’s voluntarily simple and with no extra apps/functions so you stays focused on what you’re doing. Some says it’s a default, some says it’s a perk. I think it’s a perk 😉
The environnement of the reMarkables (1 & 2) is an open source based linux. By default you can have an ssh access to your tablet, and you have the root access.
Nearly every information on that article can be found in great details here: https://remarkable.guide/
That guide is like the “hitchhiker’s guide to the remarkable world”.
They’re also the ones behind the excellent ‘reMarkable’ discord server
We are not responsible if you break your device.
Read all the documentation BEFORE acting so you know what you do.
If you want to try something undocumented / unsupported, you better ask the question on remarkable discord first.
Let’s start by stating that I’m not willing to use any cloud related functions on that tablet.
I used first codexctl to downgrade the tablet to the last toltec supported version, that is 2.15.1.1189 at the time of the article. Support for 3.X is in the tube, but not yet ready for users.
Then I used toltec to install / manage the linux packets on the reMarkable system.
Once toltec installed, I used the provided opkg commands to install Oxide
Oxide is a desktop environment for the reMarkable tablet.
Features:
See https://oxide.eeems.codes/
Then I installed the following via opkg install (I linked the project pages so you can go to see by yourself):
KOReader : An ebook reader application supporting PDF, DjVu, EPUB, FB2
Plato: An ebook reader application supporting PDF/CBZ/FB2/XPS/ePUB/DJVU reader
Sill: Gesture-based text editor (and shell) for the reMarkable tablet
VNSee: VNC client for the reMarkable tablet allowing you to use the device as a second screen
calculator
rmFM: Bare-bones file manager for the reMarkable paper tablet, built using Node.js and sas
restream: Stream your reMarkable screen over SSH
webinterface-wifi: View the web interface over wifi. For the ReMarkable Tablet
webinterface-upload: Upload button for the web interface, alternative to drag and drop. For the ReMarkable Tablet
webinterface-onboot: Enable the web interface on boot. For the ReMarkable Tablet
I also installed genie and iago (UI for drawing shapes with the pen) and genie (config based gesture launcher) following that reddit comment.
I may have installed a few others, but I’m not using them daily.
For some more, you should explore the Awesome reMarkable page (A curated list of projects related to the reMarkable tablet) as well as toltec package list / toltec entware package list
I tried reCalendar, a free online calendar generator that is also making links on dates
When updating your devices, you may sometimes encounter problems that are directly related to the way you updated and to the changes that have occurred between your version jump.
That guide does not pretend to solve all the problems, some are real issues that have to be opened on the Mayhem GITHUB issues tracker.
On the other hand, if you have followed that guide and still have a problem, your issue have better chances to be solved as it will be possible to set aside common updates related problems.
List of important steps:
You may search each each steps details in the Mayhem GITHUB Wiki, particularly in the following sections:
#hackrf #portapack #mayhem #update #upgrade #guide
Like they said, if you use a language for which serializers aren’t written yet, you can write the encoded event yourself. Here are both the recipe and the link:
0 | Magic Byte | Confluent serialization format version number; currently always 0 . |
1-4 | Schema ID | 4-byte schema ID as returned by Schema Registry. |
5-… | Data |
https://docs.confluent.io/platform/current/schema-registry/fundamentals/serdes-develop/index.html#wire-format
#kafka #avro #schema #id #raw #event #wire #format
#GPT4 is so amazing that it is a little bit frightening.
But hey, you can pour it a book and talk… to the book, isn’t it amazing ??
Seriously, the GPTs are incredible and the futur is going to change for sure.
Good or bad, well, wait and see.
PS: I can only encourage you to follow Two Minutes Papers. That channel is just so good, with simple and quick explanations, even when it’s a heavy subject like GPT4
If ever at some points Spotify on Linux refuses to start or start with fucked up graphics, there is a high probability that it’s due to hardware acceleration and a pesky update.
Spotify isn’t that much of a GUI CPU hog, so you can start it with hardware acceleration OFF and make it work again, like this:
spotify –disable-gpu
Some users reported that they needed to use –no-zygote too, but it made it instable for me.
Some had to also use –disable-software-rasterizer. I saw no changes when using it.
#spotify #gpu #linux #crash
Sometimes when using a program linked with librdkafka, you can encounter the ‘symbol lookup error.
Most of the time it’s because your program have been linked to an old version of librdkafka in your system (like outdated RedHat librdkafka yum package VS the latest build from librdkafka’s git)
Solutions:
-Check your LD_LIBRARY_PATH, be sure to find the directories containing latest librdkafka .so file is listed first
-Check what’s installed on your system
-In some case you will have to rebuild your project, having a proper LD_LIBRARY_PATH configured before
#KAFKA #C #librdkafka
In case you’re building yourself everything from source in your project, there is a good chance you once had a problem because you were using relative (like ../myressource) paths in your CFLAGS or LD_FLAGS definition and passed them down to the build system.
Short answer: when getting down in sub directories to i.e build your dependencies, the relative path can’t stay good. Only the absolute path can work.
One solution, if using GNU make, is to use something like this to compute the absolute path:
RES_RELATIVE_PATH=./path_to_my_ressource
RES_ABSOLUTE_PATH=$(realpath $(RES_RELATIVE_PATH))
CFLAGS+= -I$(RES_ABSOLUTE_PATH)
# Note: the naming is up to you. In my case, for something like cJSON, I'm using the following naming:
CJSON_RELPATH=./external/cJSON
CJSON_PATH=$(realpath $(CJSON_RELPATH))
CFLAGS+= -I$(CJSON_PATH)
You can also directly initialize with a shell call:
CJSON_CFLAGS=-I$(shell realpath "./external/cJSON")
CFLAGS+= $(CJSON_FLAGS)
#code #makefile #gnu #path #absolute #relative